Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9123307cb7cc09e46ec9adcd6e0e30ca6164665affe14d7b9f4880806f2cd12c

Tx prefix hash: efa27d097294fe306cd5ad6a1e474878f6f91e6675d96c4430751b980222f1b2
Tx public key: 5ce951c046fa7e3fa1f19abe413e1a318211dd2eab71504102a0bd6177012f5a
Timestamp: 1732991734 Timestamp [UCT]: 2024-11-30 18:35:34 Age [y:d:h:m:s]: 00:335:03:56:32
Block: 1165164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237063 RingCT/type: yes/0
Extra: 015ce951c046fa7e3fa1f19abe413e1a318211dd2eab71504102a0bd6177012f5a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3414e152be7fd82bbc873bdc311f7f6e50b4b9e1fb1c13322625894ef7a08d11 0.600000000000 1650839 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": 1165174, "vin": [ { "gen": { "height": 1165164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3414e152be7fd82bbc873bdc311f7f6e50b4b9e1fb1c13322625894ef7a08d11" } } ], "extra": [ 1, 92, 233, 81, 192, 70, 250, 126, 63, 161, 241, 154, 190, 65, 62, 26, 49, 130, 17, 221, 46, 171, 113, 80, 65, 2, 160, 189, 97, 119, 1, 47, 90, 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