Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16605a4b61c7664036493db9b6365a916c9ca96fcc51ce29a7de21515c3b073c

Tx prefix hash: 3a60d651d1b3964794a5c250c73ac0a3a901e43b1df2429c1c962890a0235439
Tx public key: 43c2735f9530c7b52d1bcd53388923ca6030cdaaea19c74c37feefa0bcba95a9
Timestamp: 1737400706 Timestamp [UCT]: 2025-01-20 19:18:26 Age [y:d:h:m:s]: 00:152:04:01:41
Block: 1201626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108429 RingCT/type: yes/0
Extra: 0143c2735f9530c7b52d1bcd53388923ca6030cdaaea19c74c37feefa0bcba95a90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 066586b57076bc2d9ffe72ce29659d53d6d2297b212ff5afd4458b69d834cfa9 0.600000000000 1688281 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": 1201636, "vin": [ { "gen": { "height": 1201626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "066586b57076bc2d9ffe72ce29659d53d6d2297b212ff5afd4458b69d834cfa9" } } ], "extra": [ 1, 67, 194, 115, 95, 149, 48, 199, 181, 45, 27, 205, 83, 56, 137, 35, 202, 96, 48, 205, 170, 234, 25, 199, 76, 55, 254, 239, 160, 188, 186, 149, 169, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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