Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20fccd9a7d3035c6cd18d05d17e017c6a70f925ea194fb3f0c9438ef0d86dc90

Tx prefix hash: ab42d560e740ae01ff853ec6306cfc971ca4c1a41d2052e3d156669ff3ef540b
Tx public key: a8ca0a2622123a1781e5f63306ac933a4095a335a1f38ab7c9734fda51ba3e07
Timestamp: 1707319193 Timestamp [UCT]: 2024-02-07 15:19:53 Age [y:d:h:m:s]: 01:020:04:15:09
Block: 952425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275436 RingCT/type: yes/0
Extra: 01a8ca0a2622123a1781e5f63306ac933a4095a335a1f38ab7c9734fda51ba3e070211000000120011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d152dd4965f183a69a29f0add2ff30fb58e6a2fc290e828db01071f41fcbf84 0.600000000000 1411407 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": 952435, "vin": [ { "gen": { "height": 952425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d152dd4965f183a69a29f0add2ff30fb58e6a2fc290e828db01071f41fcbf84" } } ], "extra": [ 1, 168, 202, 10, 38, 34, 18, 58, 23, 129, 229, 246, 51, 6, 172, 147, 58, 64, 149, 163, 53, 161, 243, 138, 183, 201, 115, 79, 218, 81, 186, 62, 7, 2, 17, 0, 0, 0, 18, 0, 17, 5, 91, 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