Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 425e25632447fdb9c63842dece51110f53cb5d38fe694a9c071662457aa51d54

Tx prefix hash: 356a953d1269dab5264b251a0ab54fc850155779fe52946c37b8e0af5ba63f0e
Tx public key: c0e0a6a74fc088995dc9cb39ff97bffd1dfd027fc442d9e9089fcdf427ee2404
Timestamp: 1694990270 Timestamp [UCT]: 2023-09-17 22:37:50 Age [y:d:h:m:s]: 01:116:14:00:49
Block: 850404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344621 RingCT/type: yes/0
Extra: 01c0e0a6a74fc088995dc9cb39ff97bffd1dfd027fc442d9e9089fcdf427ee2404021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.933810138000 dcy

stealth address amount amount idx
00: bf7ae3d9473333c0b0e63e75258a71e845462ed720ee67a40b64d6dcf1e05402 0.933810138000 1304120 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": 850414, "vin": [ { "gen": { "height": 850404 } } ], "vout": [ { "amount": 933810138, "target": { "key": "bf7ae3d9473333c0b0e63e75258a71e845462ed720ee67a40b64d6dcf1e05402" } } ], "extra": [ 1, 192, 224, 166, 167, 79, 192, 136, 153, 93, 201, 203, 57, 255, 151, 191, 253, 29, 253, 2, 127, 196, 66, 217, 233, 8, 159, 205, 244, 39, 238, 36, 4, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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