Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d6a0c335633bd3045d068d92c3763e17bc0badc944a4440acc1773ccec310c

Tx prefix hash: 7de15dd23cce912a545b3c92cf00dbd0f1e268036e1c80c9b18fed3706afa37e
Tx public key: 4556691b739ce0d04fc7c7128512aeb9d393e1ad6efc6d18f89f96af0560f52c
Timestamp: 1576424628 Timestamp [UCT]: 2019-12-15 15:43:48 Age [y:d:h:m:s]: 05:052:13:05:50
Block: 27449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184245 RingCT/type: yes/0
Extra: 014556691b739ce0d04fc7c7128512aeb9d393e1ad6efc6d18f89f96af0560f52c02110000004a9159db1e000000000000000000

1 output(s) for total of 497.795463401000 dcy

stealth address amount amount idx
00: 24b64e5b8391ae86c631ae8f02baefedf7743793d9865d2aa968acbb2270cad5 497.795463401000 45451 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": 27459, "vin": [ { "gen": { "height": 27449 } } ], "vout": [ { "amount": 497795463401, "target": { "key": "24b64e5b8391ae86c631ae8f02baefedf7743793d9865d2aa968acbb2270cad5" } } ], "extra": [ 1, 69, 86, 105, 27, 115, 156, 224, 208, 79, 199, 199, 18, 133, 18, 174, 185, 211, 147, 225, 173, 110, 252, 109, 24, 248, 159, 150, 175, 5, 96, 245, 44, 2, 17, 0, 0, 0, 74, 145, 89, 219, 30, 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