Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ba280b7a5fa2de39c5e3e2d0a42d7c87bd428c838a80557036c5251c390685

Tx prefix hash: 3477ce3e9b91173e0cd37868d8d2b3f5b675064a4226c603c3b3a6fe451fbf26
Tx public key: fd3723b51c4dc15d62c5ab5199cd569762c2f676c4101c85a6e238faf0691f8d
Timestamp: 1648244444 Timestamp [UCT]: 2022-03-25 21:40:44 Age [y:d:h:m:s]: 02:251:06:01:19
Block: 466361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699077 RingCT/type: yes/0
Extra: 01fd3723b51c4dc15d62c5ab5199cd569762c2f676c4101c85a6e238faf0691f8d021100000033a272b9cb000000000000000000

1 output(s) for total of 17.488504219000 dcy

stealth address amount amount idx
00: 699ee8e9b066e87f57c3f441a6b04641f470ce3c387d582c3c9856419fa05306 17.488504219000 884664 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": 466371, "vin": [ { "gen": { "height": 466361 } } ], "vout": [ { "amount": 17488504219, "target": { "key": "699ee8e9b066e87f57c3f441a6b04641f470ce3c387d582c3c9856419fa05306" } } ], "extra": [ 1, 253, 55, 35, 181, 28, 77, 193, 93, 98, 197, 171, 81, 153, 205, 86, 151, 98, 194, 246, 118, 196, 16, 28, 133, 166, 226, 56, 250, 240, 105, 31, 141, 2, 17, 0, 0, 0, 51, 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