Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6804d480d2f493315de06767326631b4fc9b38e057a33a5fd0a1e39b936b5230

Tx prefix hash: ae18897e35bc692fea7d485fd41d98a24f16ca3d77984046cec30979fedea547
Tx public key: e03bf96a70929d00c712eaf23688ef5062a5de7aa1daf707ee8bb2d9f79e3266
Timestamp: 1711382823 Timestamp [UCT]: 2024-03-25 16:07:03 Age [y:d:h:m:s]: 01:081:02:43:00
Block: 986137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318881 RingCT/type: yes/0
Extra: 01e03bf96a70929d00c712eaf23688ef5062a5de7aa1daf707ee8bb2d9f79e32660211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67bd4d31c0f6c461be7d8d37b0e0c60158c2c58ecd4cd7753556b5b487281d1 0.600000000000 1446364 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": 986147, "vin": [ { "gen": { "height": 986137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67bd4d31c0f6c461be7d8d37b0e0c60158c2c58ecd4cd7753556b5b487281d1" } } ], "extra": [ 1, 224, 59, 249, 106, 112, 146, 157, 0, 199, 18, 234, 242, 54, 136, 239, 80, 98, 165, 222, 122, 161, 218, 247, 7, 238, 139, 178, 217, 247, 158, 50, 102, 2, 17, 0, 0, 0, 1, 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