Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356a7c9a9e24c5e0ad46c7e816ddbd408e8a0a473494430db7988b385ab305a1

Tx prefix hash: 22592bd474d81818d2b5dc83d3173192fbfc0b85308353ef354f36aea9a1f840
Tx public key: 2a8f01ce35b605051813e1cdc67d5dae6a8c13480267b64375c8100561e44339
Timestamp: 1710209584 Timestamp [UCT]: 2024-03-12 02:13:04 Age [y:d:h:m:s]: 00:348:18:49:05
Block: 976400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249352 RingCT/type: yes/0
Extra: 012a8f01ce35b605051813e1cdc67d5dae6a8c13480267b64375c8100561e443390211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a272bac2f50e96f414487770a179dcb495de333413fb1e090b0cefe2f802f114 0.600000000000 1436393 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": 976410, "vin": [ { "gen": { "height": 976400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a272bac2f50e96f414487770a179dcb495de333413fb1e090b0cefe2f802f114" } } ], "extra": [ 1, 42, 143, 1, 206, 53, 182, 5, 5, 24, 19, 225, 205, 198, 125, 93, 174, 106, 140, 19, 72, 2, 103, 182, 67, 117, 200, 16, 5, 97, 228, 67, 57, 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