Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab6b8be04d4d0174eccf78e4cd1024030760f587cd32bcaa0bd6eb87507e3bf

Tx prefix hash: 610efca9cffb63986137721a0210cea950e642f9e8ded464ab9efb138448985c
Tx public key: fc8da164e070b6b59b8dbe03f1314791398e7e6b6a3b0e40ea0575fe72fa301b
Timestamp: 1709568934 Timestamp [UCT]: 2024-03-04 16:15:34 Age [y:d:h:m:s]: 00:326:08:39:03
Block: 971083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233577 RingCT/type: yes/0
Extra: 01fc8da164e070b6b59b8dbe03f1314791398e7e6b6a3b0e40ea0575fe72fa301b02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd569aa9aa6d917f5948bb785690e9a16c0baed6babd6a1a9f49f2cc5195c0b0 0.600000000000 1430958 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": 971093, "vin": [ { "gen": { "height": 971083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd569aa9aa6d917f5948bb785690e9a16c0baed6babd6a1a9f49f2cc5195c0b0" } } ], "extra": [ 1, 252, 141, 161, 100, 224, 112, 182, 181, 155, 141, 190, 3, 241, 49, 71, 145, 57, 142, 126, 107, 106, 59, 14, 64, 234, 5, 117, 254, 114, 250, 48, 27, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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