Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb6d3927162d3fb718529bb9dbf281c949582dc7aa0f3beea828f2ccd1dc323c

Tx prefix hash: 8373a71dcfd3e7d6626e4559e21dc43a30a82e8bb11fef9e544cf642e941863c
Tx public key: 98f2a22c97c6dbe74d4582783834fc03b395bc216d2cd29acd3ec2155574795c
Timestamp: 1720551024 Timestamp [UCT]: 2024-07-09 18:50:24 Age [y:d:h:m:s]: 01:121:14:44:50
Block: 1062133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345427 RingCT/type: yes/0
Extra: 0198f2a22c97c6dbe74d4582783834fc03b395bc216d2cd29acd3ec2155574795c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d9a8a77706434ae2ee75c1c71175703551c0b6cae8a2c1472d462afed58e4e 0.600000000000 1532634 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": 1062143, "vin": [ { "gen": { "height": 1062133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d9a8a77706434ae2ee75c1c71175703551c0b6cae8a2c1472d462afed58e4e" } } ], "extra": [ 1, 152, 242, 162, 44, 151, 198, 219, 231, 77, 69, 130, 120, 56, 52, 252, 3, 179, 149, 188, 33, 109, 44, 210, 154, 205, 62, 194, 21, 85, 116, 121, 92, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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