Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973d3c899c26f1f4723ff28f58640c7db2ff8b46a0640663db9b5457c75aa26a

Tx prefix hash: 40d07a5a7dcba08cfa9e1cf42d551a6e9c84dad19abf30b7ae3e96ad9da3da0b
Tx public key: a8aa6febbd8522165ce7482e8241e553f62b27fb416d25c48209558fc425e600
Timestamp: 1749818494 Timestamp [UCT]: 2025-06-13 12:41:34 Age [y:d:h:m:s]: 00:160:15:23:30
Block: 1304137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112555 RingCT/type: yes/0
Extra: 01a8aa6febbd8522165ce7482e8241e553f62b27fb416d25c48209558fc425e60002110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c2597d14bf80e67e054eb196e48fdfa5aac5103e5110ae512d4bb99d38293a3 0.600000000000 1791724 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": 1304147, "vin": [ { "gen": { "height": 1304137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c2597d14bf80e67e054eb196e48fdfa5aac5103e5110ae512d4bb99d38293a3" } } ], "extra": [ 1, 168, 170, 111, 235, 189, 133, 34, 22, 92, 231, 72, 46, 130, 65, 229, 83, 246, 43, 39, 251, 65, 109, 37, 196, 130, 9, 85, 143, 196, 37, 230, 0, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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