Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 230116120d4e4e8e9131a039cb06a4e7b067c27d5fa53125416b7de95e382b4e

Tx prefix hash: 14c099d25c62c8f0138716b89868f0928197ea4535c7851dcfa136279947d27e
Tx public key: 96195df42a8a48b1edcbe531a20cdf89683e85e0e8b4592290da44951b866e6f
Timestamp: 1709585337 Timestamp [UCT]: 2024-03-04 20:48:57 Age [y:d:h:m:s]: 01:254:03:05:50
Block: 971225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440351 RingCT/type: yes/0
Extra: 0196195df42a8a48b1edcbe531a20cdf89683e85e0e8b4592290da44951b866e6f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73f4bf27e1571e85efba18e62b3ea05e270bfd37779f84a35aaf3ea759758e9 0.600000000000 1431112 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": 971235, "vin": [ { "gen": { "height": 971225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73f4bf27e1571e85efba18e62b3ea05e270bfd37779f84a35aaf3ea759758e9" } } ], "extra": [ 1, 150, 25, 93, 244, 42, 138, 72, 177, 237, 203, 229, 49, 162, 12, 223, 137, 104, 62, 133, 224, 232, 180, 89, 34, 144, 218, 68, 149, 27, 134, 110, 111, 2, 17, 0, 0, 0, 3, 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