Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 127fdc1b70940c37f91dbed9b99df5b9cb6578d200d004ed015a3a80e41018df

Tx prefix hash: 7bbfdf2ba8336a4cd726b7879c97651eb2d71b69be4a54084e3913ad904b275b
Tx public key: 402d2f891992826a5457c82fcb820ad1b4599b7662df1146fe5861927c8dc096
Timestamp: 1721761637 Timestamp [UCT]: 2024-07-23 19:07:17 Age [y:d:h:m:s]: 00:215:17:09:26
Block: 1072150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154060 RingCT/type: yes/0
Extra: 01402d2f891992826a5457c82fcb820ad1b4599b7662df1146fe5861927c8dc096021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1ed06df8f6c157016f05598f82639c39f9008d60e98a85c6c33b6ac9498c409 0.600000000000 1544603 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": 1072160, "vin": [ { "gen": { "height": 1072150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1ed06df8f6c157016f05598f82639c39f9008d60e98a85c6c33b6ac9498c409" } } ], "extra": [ 1, 64, 45, 47, 137, 25, 146, 130, 106, 84, 87, 200, 47, 203, 130, 10, 209, 180, 89, 155, 118, 98, 223, 17, 70, 254, 88, 97, 146, 124, 141, 192, 150, 2, 17, 0, 0, 0, 21, 233, 20, 221, 21, 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