Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab3a781467a8a53bb9371000b1265fa76184e944034f0360398db592fdd06df

Tx prefix hash: 47efc69f021663cd75971b332b32e0ec8599d1e3663b180a65f49ea317af677e
Tx public key: 7a8a0cd9e6f051d3d45099e9526fddc5dc851a69643b2ce3a0dd2cc82f8bb031
Timestamp: 1635058663 Timestamp [UCT]: 2021-10-24 06:57:43 Age [y:d:h:m:s]: 03:039:16:07:51
Block: 359334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 806683 RingCT/type: yes/0
Extra: 017a8a0cd9e6f051d3d45099e9526fddc5dc851a69643b2ce3a0dd2cc82f8bb031021100000007f60c5d7e000000000000000000

1 output(s) for total of 39.571061576000 dcy

stealth address amount amount idx
00: b58ceaa509e943dcc07fa7daa2d79b6263b05c782951f8c814db5ed5e6c3f1de 39.571061576000 731785 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": 359344, "vin": [ { "gen": { "height": 359334 } } ], "vout": [ { "amount": 39571061576, "target": { "key": "b58ceaa509e943dcc07fa7daa2d79b6263b05c782951f8c814db5ed5e6c3f1de" } } ], "extra": [ 1, 122, 138, 12, 217, 230, 240, 81, 211, 212, 80, 153, 233, 82, 111, 221, 197, 220, 133, 26, 105, 100, 59, 44, 227, 160, 221, 44, 200, 47, 139, 176, 49, 2, 17, 0, 0, 0, 7, 246, 12, 93, 126, 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