Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b495052dc19eab1faf109c3431bf52e6ba348e374b444cec074a8f9fe75eda0

Tx prefix hash: bf692a47d59662f51a0d9894e89c34d6f8aa00060f53ea7e421d741b0da511cb
Tx public key: c89c3f48c90e967eabb55312086dd558a75ab71a92ee576ec564844aa21ce603
Timestamp: 1723884608 Timestamp [UCT]: 2024-08-17 08:50:08 Age [y:d:h:m:s]: 00:230:12:27:38
Block: 1089764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164618 RingCT/type: yes/0
Extra: 01c89c3f48c90e967eabb55312086dd558a75ab71a92ee576ec564844aa21ce60302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 761f154d8c5eec3d944984bf15487e5e4c11e2f9b9b6dbd91042c8e1dcb4d0f2 0.600000000000 1564387 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": 1089774, "vin": [ { "gen": { "height": 1089764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "761f154d8c5eec3d944984bf15487e5e4c11e2f9b9b6dbd91042c8e1dcb4d0f2" } } ], "extra": [ 1, 200, 156, 63, 72, 201, 14, 150, 126, 171, 181, 83, 18, 8, 109, 213, 88, 167, 90, 183, 26, 146, 238, 87, 110, 197, 100, 132, 74, 162, 28, 230, 3, 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