Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e93676bc3dbe79ef22cb23ea354d9abae11a3e97a316277cf6a1741e35268f2

Tx prefix hash: e7c48048ab724acde2dedb7dad0d852b8a9dbbbbe58816b607b5e176bb3a061b
Tx public key: 1d424d133fa3755b60ee6560809825172ee4441983cc9f94227ac2a8a6f1f262
Timestamp: 1700847581 Timestamp [UCT]: 2023-11-24 17:39:41 Age [y:d:h:m:s]: 01:362:22:30:06
Block: 898770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518281 RingCT/type: yes/0
Extra: 011d424d133fa3755b60ee6560809825172ee4441983cc9f94227ac2a8a6f1f26202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.645657021000 dcy

stealth address amount amount idx
00: 9b68c955b063753dc724fffd8ec4e059b7c749a44d4dc17cf9b3324acb16628e 0.645657021000 1355205 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": 898780, "vin": [ { "gen": { "height": 898770 } } ], "vout": [ { "amount": 645657021, "target": { "key": "9b68c955b063753dc724fffd8ec4e059b7c749a44d4dc17cf9b3324acb16628e" } } ], "extra": [ 1, 29, 66, 77, 19, 63, 163, 117, 91, 96, 238, 101, 96, 128, 152, 37, 23, 46, 228, 68, 25, 131, 204, 159, 148, 34, 122, 194, 168, 166, 241, 242, 98, 2, 17, 0, 0, 0, 1, 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