Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b26df38194312b9a408de2acf0b583462f9e7ac516f90e705154523d3f7060

Tx prefix hash: eaa24224068a904af6cb9874ade2836014332cf49742aad19fdcf6905c58de71
Tx public key: cb6a7a7ec22de34e37861cae49b1f044637f5282c12e2a4abf427298fb5e53f5
Timestamp: 1710803832 Timestamp [UCT]: 2024-03-18 23:17:12 Age [y:d:h:m:s]: 00:314:17:33:19
Block: 981331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225026 RingCT/type: yes/0
Extra: 01cb6a7a7ec22de34e37861cae49b1f044637f5282c12e2a4abf427298fb5e53f50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3a3ef43f9d03603222282934c0a170194abb08118859c3a183d39b55c53c3c 0.600000000000 1441426 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": 981341, "vin": [ { "gen": { "height": 981331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3a3ef43f9d03603222282934c0a170194abb08118859c3a183d39b55c53c3c" } } ], "extra": [ 1, 203, 106, 122, 126, 194, 45, 227, 78, 55, 134, 28, 174, 73, 177, 240, 68, 99, 127, 82, 130, 193, 46, 42, 74, 191, 66, 114, 152, 251, 94, 83, 245, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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