Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364aa95b6778ec1911cd490fca3f69efdcd4950d57583d94bc49f634da5902e2

Tx prefix hash: 4f6b034071d23dfd104a5686b779f1090010f083b6e9c205983becf5e407d9e5
Tx public key: 5b4d35a0d2e866df9c939ee6fbd3efb8342b7aa0ae2a191062a0243c9135b3cd
Timestamp: 1685110190 Timestamp [UCT]: 2023-05-26 14:09:50 Age [y:d:h:m:s]: 01:312:18:55:15
Block: 768551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484750 RingCT/type: yes/0
Extra: 015b4d35a0d2e866df9c939ee6fbd3efb8342b7aa0ae2a191062a0243c9135b3cd021100000009e6d27f9c000000000000000000

1 output(s) for total of 1.743699617000 dcy

stealth address amount amount idx
00: 793a87ea44102306ff6348d03bff112420e879ef37ecc4b7db60d84f6802b785 1.743699617000 1217756 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": 768561, "vin": [ { "gen": { "height": 768551 } } ], "vout": [ { "amount": 1743699617, "target": { "key": "793a87ea44102306ff6348d03bff112420e879ef37ecc4b7db60d84f6802b785" } } ], "extra": [ 1, 91, 77, 53, 160, 210, 232, 102, 223, 156, 147, 158, 230, 251, 211, 239, 184, 52, 43, 122, 160, 174, 42, 25, 16, 98, 160, 36, 60, 145, 53, 179, 205, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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