Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a88eb59ae9c769a8c7a01ee87caa367e212f157c43f69e79f13bda54e7a24a33

Tx prefix hash: 98ad273a7c44dae0a43613e8c23cfb4b0ffc768e80f05a713289a8a665cc4d2d
Tx public key: e5470086be2e8354c5690d2d8479a3c44d45e5edbfaa75cea5543f9d146e7704
Timestamp: 1737188867 Timestamp [UCT]: 2025-01-18 08:27:47 Age [y:d:h:m:s]: 00:306:18:33:02
Block: 1199910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216749 RingCT/type: yes/0
Extra: 01e5470086be2e8354c5690d2d8479a3c44d45e5edbfaa75cea5543f9d146e77040211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6a567d7632b1bc77aae38ff5de8afc9cae47857a0e913eafc772398586719e0 0.600000000000 1686547 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": 1199920, "vin": [ { "gen": { "height": 1199910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6a567d7632b1bc77aae38ff5de8afc9cae47857a0e913eafc772398586719e0" } } ], "extra": [ 1, 229, 71, 0, 134, 190, 46, 131, 84, 197, 105, 13, 45, 132, 121, 163, 196, 77, 69, 229, 237, 191, 170, 117, 206, 165, 84, 63, 157, 20, 110, 119, 4, 2, 17, 0, 0, 0, 2, 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