Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9002fec09f39fd347f02d253664448069c1fce0f4993618ad901376eb28ad1f4

Tx prefix hash: 522fd08dd8c592013f214e6559d36a694d9aa507843fe52114ee2193b0b34ecf
Tx public key: a4bbbdac01cc856e50b7d610f37e53914e5b59b470c80b32518113573eb7ec8e
Timestamp: 1734382161 Timestamp [UCT]: 2024-12-16 20:49:21 Age [y:d:h:m:s]: 00:098:03:39:55
Block: 1176705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69902 RingCT/type: yes/0
Extra: 01a4bbbdac01cc856e50b7d610f37e53914e5b59b470c80b32518113573eb7ec8e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 739e8590ee9c9fd9fe489c528acb98d9ffd803ba1a3ec51dc92864abaa1c568e 0.600000000000 1663064 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": 1176715, "vin": [ { "gen": { "height": 1176705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "739e8590ee9c9fd9fe489c528acb98d9ffd803ba1a3ec51dc92864abaa1c568e" } } ], "extra": [ 1, 164, 187, 189, 172, 1, 204, 133, 110, 80, 183, 214, 16, 243, 126, 83, 145, 78, 91, 89, 180, 112, 200, 11, 50, 81, 129, 19, 87, 62, 183, 236, 142, 2, 17, 0, 0, 0, 3, 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