Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7da7413479f2ced0fca647fe666761aaa0dcd4be2f862a62678eb7b91947e3

Tx prefix hash: 0f92406fccc40c989dc092d15da360c2f5da412bc5d6ce08d61a2ecab339a422
Tx public key: bb41285c24fb6b5fdb5e938ed1bcb7e7e76b05112bd4846cf77ed6672947b963
Timestamp: 1737192573 Timestamp [UCT]: 2025-01-18 09:29:33 Age [y:d:h:m:s]: 00:149:02:04:46
Block: 1199940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106269 RingCT/type: yes/0
Extra: 01bb41285c24fb6b5fdb5e938ed1bcb7e7e76b05112bd4846cf77ed6672947b9630211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ff6e2aa5fb93aa7061d2682ee49edef2a5ebcd2e40ce54e5f28b0e9cd3a61ea 0.600000000000 1686579 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": 1199950, "vin": [ { "gen": { "height": 1199940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ff6e2aa5fb93aa7061d2682ee49edef2a5ebcd2e40ce54e5f28b0e9cd3a61ea" } } ], "extra": [ 1, 187, 65, 40, 92, 36, 251, 107, 95, 219, 94, 147, 142, 209, 188, 183, 231, 231, 107, 5, 17, 43, 212, 132, 108, 247, 126, 214, 103, 41, 71, 185, 99, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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