Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ec03f0cbb5be3ddd965f82e6191ea22b1fbe11846e129a4abc80dcf500719a9

Tx prefix hash: 9996e19ba1b297bb5307b7e4d177e508833cd9a7c3005fdc3d8815f19701c195
Tx public key: 451074fa57cb35bbc16477a52a809b7c16a451d225cd02d4bf4493ebab47ad5d
Timestamp: 1721198029 Timestamp [UCT]: 2024-07-17 06:33:49 Age [y:d:h:m:s]: 00:266:21:00:14
Block: 1067506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190646 RingCT/type: yes/0
Extra: 01451074fa57cb35bbc16477a52a809b7c16a451d225cd02d4bf4493ebab47ad5d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf1da84886ef1f441d0a5d711793e6d50c229c026f8c8624f3f135d78cff6c23 0.600000000000 1538331 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": 1067516, "vin": [ { "gen": { "height": 1067506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf1da84886ef1f441d0a5d711793e6d50c229c026f8c8624f3f135d78cff6c23" } } ], "extra": [ 1, 69, 16, 116, 250, 87, 203, 53, 187, 193, 100, 119, 165, 42, 128, 155, 124, 22, 164, 81, 210, 37, 205, 2, 212, 191, 68, 147, 235, 171, 71, 173, 93, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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