Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 874f8b99895d10edb8e358975664edf4364d8f7624dfba267cef8f0b98c9862c

Tx prefix hash: 4e6cecd82e3f1b330c1ea4d16355e154d106ef8e123d60a24d6e124e48ce6cd0
Tx public key: 4481fe83976525b0f92fdb1b0be32e1a60016fb3507ce0d320039ddeb0ad6d25
Timestamp: 1706052519 Timestamp [UCT]: 2024-01-23 23:28:39 Age [y:d:h:m:s]: 01:317:11:26:24
Block: 941891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485745 RingCT/type: yes/0
Extra: 014481fe83976525b0f92fdb1b0be32e1a60016fb3507ce0d320039ddeb0ad6d2502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 070382057bfb05cfcff95d648ee48f53630976c6ee88d6d444c6a13395cb2aae 0.600000000000 1400049 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": 941901, "vin": [ { "gen": { "height": 941891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070382057bfb05cfcff95d648ee48f53630976c6ee88d6d444c6a13395cb2aae" } } ], "extra": [ 1, 68, 129, 254, 131, 151, 101, 37, 176, 249, 47, 219, 27, 11, 227, 46, 26, 96, 1, 111, 179, 80, 124, 224, 211, 32, 3, 157, 222, 176, 173, 109, 37, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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