Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb3831f0745ba9b82dc2acc1f89b6065b1e17ce31cd259713f08a80b1fba125

Tx prefix hash: ed337e038cf1d4e728e6446a0c32875ac24ff907e654913d09784174a6f51fa5
Tx public key: 0f5980909b863f77ec88e6e6dd29d0fd0c87d0833efd0eeee209cb3c8094fb83
Timestamp: 1722790497 Timestamp [UCT]: 2024-08-04 16:54:57 Age [y:d:h:m:s]: 00:267:14:16:43
Block: 1080679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191176 RingCT/type: yes/0
Extra: 010f5980909b863f77ec88e6e6dd29d0fd0c87d0833efd0eeee209cb3c8094fb8302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d9b79ad323c6ddde588caa97c63ef739f558cd4c6acd93feafd62a114d1ab6 0.600000000000 1554132 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": 1080689, "vin": [ { "gen": { "height": 1080679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d9b79ad323c6ddde588caa97c63ef739f558cd4c6acd93feafd62a114d1ab6" } } ], "extra": [ 1, 15, 89, 128, 144, 155, 134, 63, 119, 236, 136, 230, 230, 221, 41, 208, 253, 12, 135, 208, 131, 62, 253, 14, 238, 226, 9, 203, 60, 128, 148, 251, 131, 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