Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5f193915308bff65ce3024e39bd17b85d020ed76b213708ba436c583f38750

Tx prefix hash: 6037dfa2b72cc92d35f9ca62e2f338abd89fe854c2c438f6cce9ce40a47dc989
Tx public key: 8e0e83b48e1d234eeb734c46f02a6f9ba937801ac7e3b64f68f15b967529bd29
Timestamp: 1696940491 Timestamp [UCT]: 2023-10-10 12:21:31 Age [y:d:h:m:s]: 01:182:15:24:53
Block: 866587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391573 RingCT/type: yes/0
Extra: 018e0e83b48e1d234eeb734c46f02a6f9ba937801ac7e3b64f68f15b967529bd29021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.835098876000 dcy

stealth address amount amount idx
00: 9c84bf23b5295dc823abe1a8c9d274f570ae011b14610585cceda9abea3002d9 0.835098876000 1321199 of 0

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": 866597, "vin": [ { "gen": { "height": 866587 } } ], "vout": [ { "amount": 835098876, "target": { "key": "9c84bf23b5295dc823abe1a8c9d274f570ae011b14610585cceda9abea3002d9" } } ], "extra": [ 1, 142, 14, 131, 180, 142, 29, 35, 78, 235, 115, 76, 70, 240, 42, 111, 155, 169, 55, 128, 26, 199, 227, 182, 79, 104, 241, 91, 150, 117, 41, 189, 41, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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