Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2c810568da066b3efa3a1df2e865bf07a7a24c52101625315965147f106585

Tx prefix hash: d9361ed40173c0abc82d65d6bd3b305c09f3e19c7e16aecfa1ec43d0c8c9b09e
Tx public key: d38af8da28378659c8d7ffc2e0bfc140fccf533afcb3fbc8f525fce465800afe
Timestamp: 1736576534 Timestamp [UCT]: 2025-01-11 06:22:14 Age [y:d:h:m:s]: 00:153:21:58:22
Block: 1194852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109741 RingCT/type: yes/0
Extra: 01d38af8da28378659c8d7ffc2e0bfc140fccf533afcb3fbc8f525fce465800afe021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 957d363f1eb91d129063833e37fb0121c697d4c38cc5bda90ed1d53072d6a602 0.600000000000 1681429 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": 1194862, "vin": [ { "gen": { "height": 1194852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "957d363f1eb91d129063833e37fb0121c697d4c38cc5bda90ed1d53072d6a602" } } ], "extra": [ 1, 211, 138, 248, 218, 40, 55, 134, 89, 200, 215, 255, 194, 224, 191, 193, 64, 252, 207, 83, 58, 252, 179, 251, 200, 245, 37, 252, 228, 101, 128, 10, 254, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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