Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745ec47efd09a1de8f392cf8f5eb91f3bffc0fb413dc4dcaa47ee81027eb69ab

Tx prefix hash: f5115beb4d14a599129d583646f817ae3ef94581d82756d0c9880a7a4b9293eb
Tx public key: 0f4fcc8f3b3545b613028dc1b5c2f76bd7d3ee72eec2d85ad1261a3b92e27e45
Timestamp: 1720589766 Timestamp [UCT]: 2024-07-10 05:36:06 Age [y:d:h:m:s]: 01:119:22:03:31
Block: 1062448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344212 RingCT/type: yes/0
Extra: 010f4fcc8f3b3545b613028dc1b5c2f76bd7d3ee72eec2d85ad1261a3b92e27e4502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 323916d3ec2788a430d0ad8fbd3c71a14dd974ef50217cb0034db7951927b727 0.600000000000 1532951 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": 1062458, "vin": [ { "gen": { "height": 1062448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "323916d3ec2788a430d0ad8fbd3c71a14dd974ef50217cb0034db7951927b727" } } ], "extra": [ 1, 15, 79, 204, 143, 59, 53, 69, 182, 19, 2, 141, 193, 181, 194, 247, 107, 215, 211, 238, 114, 238, 194, 216, 90, 209, 38, 26, 59, 146, 226, 126, 69, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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