Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a1b61a34e8874695a97662f5cb9dc1f4f4b0a265fc04005cffa40ff8d17470

Tx prefix hash: 9edc7b937451c409e98b3cbc5783347a449a83b67f742a5faa745b6d213900e7
Tx public key: 967eac8de821c494612779cd1f2780d8388eca0cb7d5f6a53523415d8721999b
Timestamp: 1701856821 Timestamp [UCT]: 2023-12-06 10:00:21 Age [y:d:h:m:s]: 01:114:01:20:41
Block: 907142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342660 RingCT/type: yes/0
Extra: 01967eac8de821c494612779cd1f2780d8388eca0cb7d5f6a53523415d8721999b021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.605706110000 dcy

stealth address amount amount idx
00: d0bf10f993842dd7833108e1d5cf5bd7778797dce61407d8681a7b8197bb188b 0.605706110000 1364111 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": 907152, "vin": [ { "gen": { "height": 907142 } } ], "vout": [ { "amount": 605706110, "target": { "key": "d0bf10f993842dd7833108e1d5cf5bd7778797dce61407d8681a7b8197bb188b" } } ], "extra": [ 1, 150, 126, 172, 141, 232, 33, 196, 148, 97, 39, 121, 205, 31, 39, 128, 216, 56, 142, 202, 12, 183, 213, 246, 165, 53, 35, 65, 93, 135, 33, 153, 155, 2, 17, 0, 0, 0, 7, 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