Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578d01e36a80afd7b42f43589a5838b7a5dc634bfc2e0301f8dbecabeecc016b

Tx prefix hash: d3e1b436997e3ca0247a17afec6072ec843bee895d1878082be77bd3cbdd51c2
Tx public key: 7034a5d3d344a8f273e2e32564b6ca9a4f423199e61a28ec329699b8e3f3d11a
Timestamp: 1682806882 Timestamp [UCT]: 2023-04-29 22:21:22 Age [y:d:h:m:s]: 01:341:20:55:17
Block: 749454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505582 RingCT/type: yes/0
Extra: 017034a5d3d344a8f273e2e32564b6ca9a4f423199e61a28ec329699b8e3f3d11a0211000000027e406890000000000000000000

1 output(s) for total of 2.017195491000 dcy

stealth address amount amount idx
00: f182cae100c5469a2dc43191616887ae2174ac4baa6e32c0f60c54981fd1e417 2.017195491000 1197427 of 0

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": 749464, "vin": [ { "gen": { "height": 749454 } } ], "vout": [ { "amount": 2017195491, "target": { "key": "f182cae100c5469a2dc43191616887ae2174ac4baa6e32c0f60c54981fd1e417" } } ], "extra": [ 1, 112, 52, 165, 211, 211, 68, 168, 242, 115, 226, 227, 37, 100, 182, 202, 154, 79, 66, 49, 153, 230, 26, 40, 236, 50, 150, 153, 184, 227, 243, 209, 26, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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