Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a6dba2e2eb7dede8dc7ab308f6d815bec3250808f95ef7d1b19deaadac3796

Tx prefix hash: 00fa99803eece097ecb1ee5c0ee2f72239ae133e7b89d9496ff3cfd52526ea59
Tx public key: c56b99e68d009e9e7aa4c662b3e2ffce532b699ee9f423f5573d1e2ac5e6dfd6
Timestamp: 1736753908 Timestamp [UCT]: 2025-01-13 07:38:28 Age [y:d:h:m:s]: 00:064:03:34:47
Block: 1196311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45636 RingCT/type: yes/0
Extra: 01c56b99e68d009e9e7aa4c662b3e2ffce532b699ee9f423f5573d1e2ac5e6dfd6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e9a331d015fa4bb97557e9d6ad57bde9b945db3e9786e8cb589164e84493e46 0.600000000000 1682910 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": 1196321, "vin": [ { "gen": { "height": 1196311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e9a331d015fa4bb97557e9d6ad57bde9b945db3e9786e8cb589164e84493e46" } } ], "extra": [ 1, 197, 107, 153, 230, 141, 0, 158, 158, 122, 164, 198, 98, 179, 226, 255, 206, 83, 43, 105, 158, 233, 244, 35, 245, 87, 61, 30, 42, 197, 230, 223, 214, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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