Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6ba6dfe046aed4e76a42bcf31abc5f3d054bc3f0b33365cbb897d5ba9de46e

Tx prefix hash: 45cdb5cfc3fe3926a3b58ca8bbc125ad62848a41ce1a19cad2edfb78bcf112b3
Tx public key: 36b6151c2b5b8cb3d2e96ebb7681147b0ade8fe6f9cf951fd23e1c1d169b799a
Timestamp: 1722600131 Timestamp [UCT]: 2024-08-02 12:02:11 Age [y:d:h:m:s]: 01:097:07:02:32
Block: 1079110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328018 RingCT/type: yes/0
Extra: 0136b6151c2b5b8cb3d2e96ebb7681147b0ade8fe6f9cf951fd23e1c1d169b799a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7da3d75222b20e2e1c303c88d9e81854c7de8ce3f8a3a34d19eefe5f777aca 0.600000000000 1551923 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": 1079120, "vin": [ { "gen": { "height": 1079110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7da3d75222b20e2e1c303c88d9e81854c7de8ce3f8a3a34d19eefe5f777aca" } } ], "extra": [ 1, 54, 182, 21, 28, 43, 91, 140, 179, 210, 233, 110, 187, 118, 129, 20, 123, 10, 222, 143, 230, 249, 207, 149, 31, 210, 62, 28, 29, 22, 155, 121, 154, 2, 17, 0, 0, 0, 3, 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