Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 293e7ce3db06a2709615f61b10a828c93308dfe57778f19ae958eda05e755edd

Tx prefix hash: 10666b1c6f536780165049a61c423e177b5e9bb18d1cb481513213083552ff2f
Tx public key: 021d7c9896b58b82f9773b6e4934363521166d6c4dfc50e2738f476df5d1f6e4
Timestamp: 1737262192 Timestamp [UCT]: 2025-01-19 04:49:52 Age [y:d:h:m:s]: 00:150:21:19:07
Block: 1200479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107560 RingCT/type: yes/0
Extra: 01021d7c9896b58b82f9773b6e4934363521166d6c4dfc50e2738f476df5d1f6e4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fdf1d33b4600b7bf0c5a24ad843f0de57958ee0cdde45901688381dccf058c2 0.600000000000 1687124 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": 1200489, "vin": [ { "gen": { "height": 1200479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fdf1d33b4600b7bf0c5a24ad843f0de57958ee0cdde45901688381dccf058c2" } } ], "extra": [ 1, 2, 29, 124, 152, 150, 181, 139, 130, 249, 119, 59, 110, 73, 52, 54, 53, 33, 22, 109, 108, 77, 252, 80, 226, 115, 143, 71, 109, 245, 209, 246, 228, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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