Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ceff5bb14c2bf10577c9c8c2c0a23eea2f59e93e5f31f2e9a911d28c0b55557e

Tx prefix hash: b888df5fae6108a46ee8eb864ad76a32c282cf7fcd1596ae90bd8d17f6af369a
Tx public key: e6033c92ba8308661aa4dcfb1e41d1219fa33829e6c970dd3a67bc50cee7d319
Timestamp: 1685942827 Timestamp [UCT]: 2023-06-05 05:27:07 Age [y:d:h:m:s]: 01:270:04:45:21
Block: 775450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454277 RingCT/type: yes/0
Extra: 01e6033c92ba8308661aa4dcfb1e41d1219fa33829e6c970dd3a67bc50cee7d319021100000004faf35c9c000000000000000000

1 output(s) for total of 1.654292921000 dcy

stealth address amount amount idx
00: 04213268f2f04ab131b43d173e359aeb341ba8bec3841bb5c64e992bdbfaab62 1.654292921000 1224961 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": 775460, "vin": [ { "gen": { "height": 775450 } } ], "vout": [ { "amount": 1654292921, "target": { "key": "04213268f2f04ab131b43d173e359aeb341ba8bec3841bb5c64e992bdbfaab62" } } ], "extra": [ 1, 230, 3, 60, 146, 186, 131, 8, 102, 26, 164, 220, 251, 30, 65, 209, 33, 159, 163, 56, 41, 230, 201, 112, 221, 58, 103, 188, 80, 206, 231, 211, 25, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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