Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22f76a8166d74e4acf0e479af5349142f032f0d8747976c404c1f47e0c2e599a

Tx prefix hash: c35d87576d4eed4f242d1677925c4ac30057aa7b9a27b1f066056bdff8113813
Tx public key: 9e3a9e8e21ebfaa94b95d93216fdec85555227afefb055b1142fb8da07ef335f
Timestamp: 1759228057 Timestamp [UCT]: 2025-09-30 10:27:37 Age [y:d:h:m:s]: 00:123:05:40:40
Block: 1379651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88072 RingCT/type: yes/0
Extra: 019e3a9e8e21ebfaa94b95d93216fdec85555227afefb055b1142fb8da07ef335f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c06ba582e1527df312803ffd9c4595c7a52a0bfffe781820a8d1b113e85c252b 0.600000000000 1867758 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": 1379661, "vin": [ { "gen": { "height": 1379651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c06ba582e1527df312803ffd9c4595c7a52a0bfffe781820a8d1b113e85c252b" } } ], "extra": [ 1, 158, 58, 158, 142, 33, 235, 250, 169, 75, 149, 217, 50, 22, 253, 236, 133, 85, 82, 39, 175, 239, 176, 85, 177, 20, 47, 184, 218, 7, 239, 51, 95, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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