Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1965ec50a7036fff8a69497db43d967dfed3b19336aa67e1f0a2668a1e9f98b1

Tx prefix hash: 8ae62094ec8a451080d0d415ee81700ad780627f690a76de72ca4a7121beefcf
Tx public key: 7eddf1ea814f0b1cfdd1fe1681af9e814817a2ad3fee49a3cdfde1cb3b7c4ce4
Timestamp: 1741238600 Timestamp [UCT]: 2025-03-06 05:23:20 Age [y:d:h:m:s]: 00:006:12:11:11
Block: 1233171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4666 RingCT/type: yes/0
Extra: 017eddf1ea814f0b1cfdd1fe1681af9e814817a2ad3fee49a3cdfde1cb3b7c4ce40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a65160e993d2600239779f177739f558d62bb128298e0a1747d80411b0e731e8 0.600000000000 1720090 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": 1233181, "vin": [ { "gen": { "height": 1233171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a65160e993d2600239779f177739f558d62bb128298e0a1747d80411b0e731e8" } } ], "extra": [ 1, 126, 221, 241, 234, 129, 79, 11, 28, 253, 209, 254, 22, 129, 175, 158, 129, 72, 23, 162, 173, 63, 238, 73, 163, 205, 253, 225, 203, 59, 124, 76, 228, 2, 17, 0, 0, 0, 1, 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