Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f856f76ded2cdc04ba199cfb726e17835bb35e6e71e5674360ffb50315055ee

Tx prefix hash: 106acc406b95aa704f317b7911ad52874ab5da61fd88110e8227871df77534f7
Tx public key: 0c6089223f39ecdb1b75f640cf912b98beae63cc8cb0d1c26bd6e13083a4f9e9
Timestamp: 1726817097 Timestamp [UCT]: 2024-09-20 07:24:57 Age [y:d:h:m:s]: 00:111:20:13:22
Block: 1114073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79966 RingCT/type: yes/0
Extra: 010c6089223f39ecdb1b75f640cf912b98beae63cc8cb0d1c26bd6e13083a4f9e902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6403f939a20c3fc81b8e10ab5b44b1b3f70e9c0591733a8966f178b0183bea50 0.600000000000 1593870 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": 1114083, "vin": [ { "gen": { "height": 1114073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6403f939a20c3fc81b8e10ab5b44b1b3f70e9c0591733a8966f178b0183bea50" } } ], "extra": [ 1, 12, 96, 137, 34, 63, 57, 236, 219, 27, 117, 246, 64, 207, 145, 43, 152, 190, 174, 99, 204, 140, 176, 209, 194, 107, 214, 225, 48, 131, 164, 249, 233, 2, 17, 0, 0, 0, 6, 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