Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf7368770b884a38f164ee9c8b0e5fcb7e76f0dd02f7e5f1ce6f287d6df3193

Tx prefix hash: f9121840b8e6e840a7b388563523509e3df25eeea1850fe595e41f5994101111
Tx public key: c3c83448d3af6a81c3492ad005d8328c77c7442564ad59ff2e1d7464e5af588a
Timestamp: 1749384491 Timestamp [UCT]: 2025-06-08 12:08:11 Age [y:d:h:m:s]: 00:157:17:03:36
Block: 1300621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110385 RingCT/type: yes/0
Extra: 01c3c83448d3af6a81c3492ad005d8328c77c7442564ad59ff2e1d7464e5af588a02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52afd0c3507ed005ccba401d74bb30c186e67efe4d19e2a29a804168a840e63 0.600000000000 1788170 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": 1300631, "vin": [ { "gen": { "height": 1300621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52afd0c3507ed005ccba401d74bb30c186e67efe4d19e2a29a804168a840e63" } } ], "extra": [ 1, 195, 200, 52, 72, 211, 175, 106, 129, 195, 73, 42, 208, 5, 216, 50, 140, 119, 199, 68, 37, 100, 173, 89, 255, 46, 29, 116, 100, 229, 175, 88, 138, 2, 17, 0, 0, 0, 4, 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