Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3469d536298f3d372fc5b2cb2bd997d50500867748c0739736291024033266a9

Tx prefix hash: 855cc118eaedfae7c41617a83aafa529382cd1b1c0a0aeb2baf95cd4249066df
Tx public key: f82905f5bbe7707071f2d4d2826e0d6eb5ca402714faa3f580ed465975c076e6
Timestamp: 1633432008 Timestamp [UCT]: 2021-10-05 11:06:48 Age [y:d:h:m:s]: 03:054:08:42:01
Block: 347109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 815939 RingCT/type: yes/0
Extra: 01f82905f5bbe7707071f2d4d2826e0d6eb5ca402714faa3f580ed465975c076e6021100000001a272b9cb000000000000000000

1 output(s) for total of 43.439440047000 dcy

stealth address amount amount idx
00: a049cc1eea14290b3e52837bb821b7bc9a18fc641f839b983f5d8b33b5f0eea3 43.439440047000 711391 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": 347119, "vin": [ { "gen": { "height": 347109 } } ], "vout": [ { "amount": 43439440047, "target": { "key": "a049cc1eea14290b3e52837bb821b7bc9a18fc641f839b983f5d8b33b5f0eea3" } } ], "extra": [ 1, 248, 41, 5, 245, 187, 231, 112, 112, 113, 242, 212, 210, 130, 110, 13, 110, 181, 202, 64, 39, 20, 250, 163, 245, 128, 237, 70, 89, 117, 192, 118, 230, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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