Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81542594a4d760666d656a71d9f32a1fb6d4e106f5a2f64110f84d9d9d9cb5fe

Tx prefix hash: f25c7018f69ab1508b83275cf29a72498a1b5d1906a6d2c9b0428edbe80c8947
Tx public key: 617838845b1427e6b3fece27e5f104473b3e8fba46efdca28a26838d768d146a
Timestamp: 1766179937 Timestamp [UCT]: 2025-12-19 21:32:17 Age [y:d:h:m:s]: 00:002:01:08:08
Block: 1437279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1459 RingCT/type: yes/0
Extra: 01617838845b1427e6b3fece27e5f104473b3e8fba46efdca28a26838d768d146a0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2457f7226172fb6f3ee10a4dc16b2bb47fd54813353d0d99c17274e2e45d330 0.600000000000 1926086 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": 1437289, "vin": [ { "gen": { "height": 1437279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2457f7226172fb6f3ee10a4dc16b2bb47fd54813353d0d99c17274e2e45d330" } } ], "extra": [ 1, 97, 120, 56, 132, 91, 20, 39, 230, 179, 254, 206, 39, 229, 241, 4, 71, 59, 62, 143, 186, 70, 239, 220, 162, 138, 38, 131, 141, 118, 141, 20, 106, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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