Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944d340b83e248f339c127f46a88b34a17b85ccc417ec1cab0b829a26c03ac54

Tx prefix hash: f9216da10866d4468f58810b7b651b06efa7d30b05328fcd5b7b391d0508be4d
Tx public key: 0f6df67068d720b9a291f3356d80013a84faf02d428e0b4697c7cae1553a594c
Timestamp: 1736542716 Timestamp [UCT]: 2025-01-10 20:58:36 Age [y:d:h:m:s]: 00:346:10:01:01
Block: 1194562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245133 RingCT/type: yes/0
Extra: 010f6df67068d720b9a291f3356d80013a84faf02d428e0b4697c7cae1553a594c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6f553afeedde4c41c76a776d8400855b588ed8f76d1cab1fe4399b3ce4d856 0.600000000000 1681139 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": 1194572, "vin": [ { "gen": { "height": 1194562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6f553afeedde4c41c76a776d8400855b588ed8f76d1cab1fe4399b3ce4d856" } } ], "extra": [ 1, 15, 109, 246, 112, 104, 215, 32, 185, 162, 145, 243, 53, 109, 128, 1, 58, 132, 250, 240, 45, 66, 142, 11, 70, 151, 199, 202, 225, 85, 58, 89, 76, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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