Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594e0fa1a04d72a3f5f591a7a7a205bb07371448059711523f3b83fbe60f00f6

Tx prefix hash: e92eb560f8bdfc48fc29fcd697b3bc5eacd79b799e0ba1a69df3562f3c504131
Tx public key: 44a8b85a69d8eee97fbfa7f25a71679b4fe4b610232c255eee0ea6988255fe02
Timestamp: 1737728127 Timestamp [UCT]: 2025-01-24 14:15:27 Age [y:d:h:m:s]: 00:144:10:44:58
Block: 1204336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102968 RingCT/type: yes/0
Extra: 0144a8b85a69d8eee97fbfa7f25a71679b4fe4b610232c255eee0ea6988255fe020211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd29ca00561f362aa2573e91c09d28ecfd21757a0ff2899d42d107cbde6a222d 0.600000000000 1691021 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": 1204346, "vin": [ { "gen": { "height": 1204336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd29ca00561f362aa2573e91c09d28ecfd21757a0ff2899d42d107cbde6a222d" } } ], "extra": [ 1, 68, 168, 184, 90, 105, 216, 238, 233, 127, 191, 167, 242, 90, 113, 103, 155, 79, 228, 182, 16, 35, 44, 37, 94, 238, 14, 166, 152, 130, 85, 254, 2, 2, 17, 0, 0, 0, 6, 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