Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6d24f282543a5f6f76b356cd675e1c480366906688b2bca2054f4f3230fd56

Tx prefix hash: e1f6915f02510e8a268063ca7e4992f8961fcf40f6b0643e1ed115de3523a23d
Tx public key: 5f0862ae3bff8e8439c5cb2e30d313bf28d8cda5608537f5dbed2556c7cd21f0
Timestamp: 1711950571 Timestamp [UCT]: 2024-04-01 05:49:31 Age [y:d:h:m:s]: 01:054:21:06:38
Block: 990782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300261 RingCT/type: yes/0
Extra: 015f0862ae3bff8e8439c5cb2e30d313bf28d8cda5608537f5dbed2556c7cd21f002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0a73f974c26ec6849997435e10a80eb4407d4a449e76f5540127af81badd94 0.600000000000 1451110 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": 990792, "vin": [ { "gen": { "height": 990782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0a73f974c26ec6849997435e10a80eb4407d4a449e76f5540127af81badd94" } } ], "extra": [ 1, 95, 8, 98, 174, 59, 255, 142, 132, 57, 197, 203, 46, 48, 211, 19, 191, 40, 216, 205, 165, 96, 133, 55, 245, 219, 237, 37, 86, 199, 205, 33, 240, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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