Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326ea719fb068bdd8f522c85efdd73565583183334e8c6e0da8dca599810ef24

Tx prefix hash: dbbd82c4663ecbf9f1408fd2c8fe0b4822a58137e0c55cf6444b755067fcd0ea
Tx public key: 074e51e83195ad689ecc8495028ac549efde94fc68ee1c57f3510e3a4aa073cb
Timestamp: 1682917659 Timestamp [UCT]: 2023-05-01 05:07:39 Age [y:d:h:m:s]: 01:345:17:35:34
Block: 750380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508338 RingCT/type: yes/0
Extra: 01074e51e83195ad689ecc8495028ac549efde94fc68ee1c57f3510e3a4aa073cb02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.002994538000 dcy

stealth address amount amount idx
00: 917fcea11a02720084acd9ea7e15f8b2cd8e8677b59c5e5eec4e8b93c6d51154 2.002994538000 1198449 of 0

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": 750390, "vin": [ { "gen": { "height": 750380 } } ], "vout": [ { "amount": 2002994538, "target": { "key": "917fcea11a02720084acd9ea7e15f8b2cd8e8677b59c5e5eec4e8b93c6d51154" } } ], "extra": [ 1, 7, 78, 81, 232, 49, 149, 173, 104, 158, 204, 132, 149, 2, 138, 197, 73, 239, 222, 148, 252, 104, 238, 28, 87, 243, 81, 14, 58, 74, 160, 115, 203, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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