Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4adeb8943fc6b40f9d1c9fae015ecd6a05a45126a1ad79cc5f05f38ce71b8ca0

Tx prefix hash: eea9ff53fb29500a5acfa0d610459481869c042399787d666fb50c38ed3d8505
Tx public key: 6193547700de0714e9e2836318d47ff0ada70137c95f4f488e623e5c848212a7
Timestamp: 1695835214 Timestamp [UCT]: 2023-09-27 17:20:14 Age [y:d:h:m:s]: 01:193:23:30:16
Block: 857420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399692 RingCT/type: yes/0
Extra: 016193547700de0714e9e2836318d47ff0ada70137c95f4f488e623e5c848212a702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.885139361000 dcy

stealth address amount amount idx
00: 745d2a3d2ba4639f1a137ee3c2169c46a08f432e7dde1c7b6d4517baa4696b14 0.885139361000 1311540 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": 857430, "vin": [ { "gen": { "height": 857420 } } ], "vout": [ { "amount": 885139361, "target": { "key": "745d2a3d2ba4639f1a137ee3c2169c46a08f432e7dde1c7b6d4517baa4696b14" } } ], "extra": [ 1, 97, 147, 84, 119, 0, 222, 7, 20, 233, 226, 131, 99, 24, 212, 127, 240, 173, 167, 1, 55, 201, 95, 79, 72, 142, 98, 62, 92, 132, 130, 18, 167, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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