Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362e94f940ba5ac351166e5979abca2179328976a7323a9e0b18ecd5114c60be

Tx prefix hash: 8e45a747b9bf6fb7c3211df9d66bd52a0d13248c5e04ace86948f7d2e5df678f
Tx public key: e22d7ddf53b2f922236f69548c3d350d0fc62e5c295563776d76039df2db3f54
Timestamp: 1736783709 Timestamp [UCT]: 2025-01-13 15:55:09 Age [y:d:h:m:s]: 00:063:17:05:02
Block: 1196558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45313 RingCT/type: yes/0
Extra: 01e22d7ddf53b2f922236f69548c3d350d0fc62e5c295563776d76039df2db3f540211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c5697e5d453b03ac7c86a20789b40ec15b28a8e0b47510b2ae8624ca95cc12b 0.600000000000 1683157 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": 1196568, "vin": [ { "gen": { "height": 1196558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c5697e5d453b03ac7c86a20789b40ec15b28a8e0b47510b2ae8624ca95cc12b" } } ], "extra": [ 1, 226, 45, 125, 223, 83, 178, 249, 34, 35, 111, 105, 84, 140, 61, 53, 13, 15, 198, 46, 92, 41, 85, 99, 119, 109, 118, 3, 157, 242, 219, 63, 84, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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