Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d113af0762b0e6f10e98f3da0417787856f540c30044edbf078163dc38e1952c

Tx prefix hash: 013f768e5badc18e95d4f68d21489852455edce8a704bb6c452c033af7164c71
Tx public key: 443340f5b5246aee1b566eb0ddce772057d740f67b2222de49e75c958e17e44b
Timestamp: 1696889117 Timestamp [UCT]: 2023-10-09 22:05:17 Age [y:d:h:m:s]: 01:188:10:19:36
Block: 866159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395711 RingCT/type: yes/0
Extra: 01443340f5b5246aee1b566eb0ddce772057d740f67b2222de49e75c958e17e44b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.828048369000 dcy

stealth address amount amount idx
00: 3fd726d07d6e1711a64633f047d67aab2d9c8265723cb3a6f9cb9a5879c72845 0.828048369000 1320731 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": 866169, "vin": [ { "gen": { "height": 866159 } } ], "vout": [ { "amount": 828048369, "target": { "key": "3fd726d07d6e1711a64633f047d67aab2d9c8265723cb3a6f9cb9a5879c72845" } } ], "extra": [ 1, 68, 51, 64, 245, 181, 36, 106, 238, 27, 86, 110, 176, 221, 206, 119, 32, 87, 215, 64, 246, 123, 34, 34, 222, 73, 231, 92, 149, 142, 23, 228, 75, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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