Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3316ad192e40abb86560c16deb9de07f9f59c8139109cd11280a6afef11d2341

Tx prefix hash: ee1814191285403ecdb5585e6b4c8f95d499fb0452ec0886bd9498620ccd1a8b
Tx public key: 74fb8ddec610b3908b579bc5ba0b95f89e55dcb4461ac8dc1516dee6ba9cb26d
Timestamp: 1715600871 Timestamp [UCT]: 2024-05-13 11:47:51 Age [y:d:h:m:s]: 01:002:20:20:23
Block: 1021107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262928 RingCT/type: yes/0
Extra: 0174fb8ddec610b3908b579bc5ba0b95f89e55dcb4461ac8dc1516dee6ba9cb26d02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ea23d7a469b5a1c4d4637e389fb6e2445d74f3ab325b624622c6e772dbcca63 0.600000000000 1485320 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": 1021117, "vin": [ { "gen": { "height": 1021107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ea23d7a469b5a1c4d4637e389fb6e2445d74f3ab325b624622c6e772dbcca63" } } ], "extra": [ 1, 116, 251, 141, 222, 198, 16, 179, 144, 139, 87, 155, 197, 186, 11, 149, 248, 158, 85, 220, 180, 70, 26, 200, 220, 21, 22, 222, 230, 186, 156, 178, 109, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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