Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 843e3282275896efe4ddef67ff6c5f60487299ac09ba4eea2a7fbfb6f76bec1b

Tx prefix hash: fc0c1d7f5222417e20e1ccdce6116c1dd7910cb339acf003174c5ea5f6bfeecd
Tx public key: bef6eacf230a064652b5cf8a767a04371bbba661fca0b24a3f70e9fe4f2c42c2
Timestamp: 1700939229 Timestamp [UCT]: 2023-11-25 19:07:09 Age [y:d:h:m:s]: 01:341:23:50:40
Block: 899524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503315 RingCT/type: yes/0
Extra: 01bef6eacf230a064652b5cf8a767a04371bbba661fca0b24a3f70e9fe4f2c42c202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.641953487000 dcy

stealth address amount amount idx
00: b61abeb2e3ef82f8baa38e94dbb3def0a2f1017fdfadd517e42bb8e3b9f4f90a 0.641953487000 1355979 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": 899534, "vin": [ { "gen": { "height": 899524 } } ], "vout": [ { "amount": 641953487, "target": { "key": "b61abeb2e3ef82f8baa38e94dbb3def0a2f1017fdfadd517e42bb8e3b9f4f90a" } } ], "extra": [ 1, 190, 246, 234, 207, 35, 10, 6, 70, 82, 181, 207, 138, 118, 122, 4, 55, 27, 187, 166, 97, 252, 160, 178, 74, 63, 112, 233, 254, 79, 44, 66, 194, 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