Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0c7305734e9b9daef0834acf1c7c20596f5955f1e4aa1d560927a5fef8cb1606

Tx prefix hash: 988dd9d82f995789aaaf2a117a44b7018826d8c579d32b1f3b049993be6c49ef
Tx public key: 63e6b160dd16ce3dc89c5b756e50e95d62dc7882c1fedc73127d551941079f40
Timestamp: 1733210760 Timestamp [UCT]: 2024-12-03 07:26:00 Age [y:d:h:m:s]: 00:133:15:47:02
Block: 1166977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95335 RingCT/type: yes/0
Extra: 0163e6b160dd16ce3dc89c5b756e50e95d62dc7882c1fedc73127d551941079f4002110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e6ae15d2ab00cea1645339bdec1c2c4383d1b57e61c1eec1cf15eebaa4698d0 0.600000000000 1652670 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1166987, "vin": [ { "gen": { "height": 1166977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e6ae15d2ab00cea1645339bdec1c2c4383d1b57e61c1eec1cf15eebaa4698d0" } } ], "extra": [ 1, 99, 230, 177, 96, 221, 22, 206, 61, 200, 156, 91, 117, 110, 80, 233, 93, 98, 220, 120, 130, 193, 254, 220, 115, 18, 125, 85, 25, 65, 7, 159, 64, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8