Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f631e23285496dd023803040d30096ffb30cbfd763a61059271a5e61ce806fc9

Tx prefix hash: 1c380e4186e6c9b427ea135b040007a91168efd27145f27c13d3188b8ef09269
Tx public key: 294167420d416fd1e9a2c09fd31826c023cce2e30357231712494e5c581c4cc1
Timestamp: 1673567462 Timestamp [UCT]: 2023-01-12 23:51:02 Age [y:d:h:m:s]: 02:088:11:56:44
Block: 673474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584919 RingCT/type: yes/0
Extra: 01294167420d416fd1e9a2c09fd31826c023cce2e30357231712494e5c581c4cc10211000000018b7b6602000000000000000000

1 output(s) for total of 3.601645945000 dcy

stealth address amount amount idx
00: 0a4eb19c326a29082b0fab9823b9829909a540eafdbf6f9e645f961b01e9891a 3.601645945000 1115083 of 0

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": 673484, "vin": [ { "gen": { "height": 673474 } } ], "vout": [ { "amount": 3601645945, "target": { "key": "0a4eb19c326a29082b0fab9823b9829909a540eafdbf6f9e645f961b01e9891a" } } ], "extra": [ 1, 41, 65, 103, 66, 13, 65, 111, 209, 233, 162, 192, 159, 211, 24, 38, 192, 35, 204, 226, 227, 3, 87, 35, 23, 18, 73, 78, 92, 88, 28, 76, 193, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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