Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97cc872ac467af93263d61cb02f55aaa619624b2e9343d3d125f30ce4440c80c

Tx prefix hash: 27769c4f26f671340a18d36116445717e6c1a8755cfeb21c65f96de7f317865a
Tx public key: 720cb112a2c2d0851efd7d16b318242f971d62a3e530ab644a889cb57aa0f0b4
Timestamp: 1711883360 Timestamp [UCT]: 2024-03-31 11:09:20 Age [y:d:h:m:s]: 01:234:20:19:53
Block: 990283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426510 RingCT/type: yes/0
Extra: 01720cb112a2c2d0851efd7d16b318242f971d62a3e530ab644a889cb57aa0f0b402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0cde225dd1b528a9604f29207dc94471c5fe68e159d745f58627c86dd665d23 0.600000000000 1450605 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": 990293, "vin": [ { "gen": { "height": 990283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0cde225dd1b528a9604f29207dc94471c5fe68e159d745f58627c86dd665d23" } } ], "extra": [ 1, 114, 12, 177, 18, 162, 194, 208, 133, 30, 253, 125, 22, 179, 24, 36, 47, 151, 29, 98, 163, 229, 48, 171, 100, 74, 136, 156, 181, 122, 160, 240, 180, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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