Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d8135e43c5201dc3af3f13f3a1f27653b0765c2754c27cc05180bf6441f116

Tx prefix hash: e7264dd7daf3d09287242e2ba7625533c45eb9f3ddcaeed080782654bd5abad9
Tx public key: dbd34aa4150c751a047f0a75282198a3fbc9724781f124f64fdfd5f1a4308e80
Timestamp: 1647062404 Timestamp [UCT]: 2022-03-12 05:20:04 Age [y:d:h:m:s]: 02:286:20:29:38
Block: 456608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724546 RingCT/type: yes/0
Extra: 01dbd34aa4150c751a047f0a75282198a3fbc9724781f124f64fdfd5f1a4308e80021100000013bf7ee4e7000000000000000000

1 output(s) for total of 18.839458601000 dcy

stealth address amount amount idx
00: 0a7b1c4198830946b3e7fb9c60c259580dd1033fffeb2f3eafde97d8d6a6d29a 18.839458601000 872701 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": 456618, "vin": [ { "gen": { "height": 456608 } } ], "vout": [ { "amount": 18839458601, "target": { "key": "0a7b1c4198830946b3e7fb9c60c259580dd1033fffeb2f3eafde97d8d6a6d29a" } } ], "extra": [ 1, 219, 211, 74, 164, 21, 12, 117, 26, 4, 127, 10, 117, 40, 33, 152, 163, 251, 201, 114, 71, 129, 241, 36, 246, 79, 223, 213, 241, 164, 48, 142, 128, 2, 17, 0, 0, 0, 19, 191, 126, 228, 231, 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