Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9c1147e0fc8eddf16511bd4f1c7d4962bb1f3ce3550fcf6c246f8bda70bd122

Tx prefix hash: bcd5ccb505952dd18401d40bd5944d6a018883e5c6a4bb56d56654b5cee86edf
Tx public key: b5a1d6089bdc921e3414c67bc225806d714f58d4b579c4889b73d09ca6e14d8e
Timestamp: 1749326691 Timestamp [UCT]: 2025-06-07 20:04:51 Age [y:d:h:m:s]: 00:166:20:52:50
Block: 1300141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116938 RingCT/type: yes/0
Extra: 01b5a1d6089bdc921e3414c67bc225806d714f58d4b579c4889b73d09ca6e14d8e02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6972a6299a4c26334b1d67807e147a944edddf5cf411be3b849065a350ccd40 0.600000000000 1787688 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": 1300151, "vin": [ { "gen": { "height": 1300141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6972a6299a4c26334b1d67807e147a944edddf5cf411be3b849065a350ccd40" } } ], "extra": [ 1, 181, 161, 214, 8, 155, 220, 146, 30, 52, 20, 198, 123, 194, 37, 128, 109, 113, 79, 88, 212, 181, 121, 196, 136, 155, 115, 208, 156, 166, 225, 77, 142, 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