Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f3c15c527b9d84c2d682d5eda9ebc04c0529cdcaf6e06778a04577290fdfd1c

Tx prefix hash: dda69b86a914bab66a667e505bcf16eff3ea8cf1aefab0092fa2469bb0e7b4e6
Tx public key: 96f904fffcf938b3b5de74be75cc89f5c752fac8498836b6504d6566c0f8099f
Timestamp: 1720529994 Timestamp [UCT]: 2024-07-09 12:59:54 Age [y:d:h:m:s]: 00:249:03:01:16
Block: 1061956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177990 RingCT/type: yes/0
Extra: 0196f904fffcf938b3b5de74be75cc89f5c752fac8498836b6504d6566c0f8099f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915e9f431fd7c7c4b04fdc975c219bdc88a3ee8c9703b83456493c1300296e37 0.600000000000 1532455 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": 1061966, "vin": [ { "gen": { "height": 1061956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915e9f431fd7c7c4b04fdc975c219bdc88a3ee8c9703b83456493c1300296e37" } } ], "extra": [ 1, 150, 249, 4, 255, 252, 249, 56, 179, 181, 222, 116, 190, 117, 204, 137, 245, 199, 82, 250, 200, 73, 136, 54, 182, 80, 77, 101, 102, 192, 248, 9, 159, 2, 17, 0, 0, 0, 5, 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