Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49094d98e1e7b0012b360d71021cbe10324b1916cc9754d45d49e454bfbd1c0

Tx prefix hash: 606b600a9f2323c4ac1514ea1a028d1bcf0635ed2d41a79cafa246242ff3f4b8
Tx public key: 7c46f4d2d1cf7f51e6caae16ac5d3e06578bd62aaf5fdca616d4cda5d4a8fe2b
Timestamp: 1708007210 Timestamp [UCT]: 2024-02-15 14:26:50 Age [y:d:h:m:s]: 01:087:21:44:02
Block: 958123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323888 RingCT/type: yes/0
Extra: 017c46f4d2d1cf7f51e6caae16ac5d3e06578bd62aaf5fdca616d4cda5d4a8fe2b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76b6a46ba5978940d2980d208de0a995aca078b0d288f6d808e66a6d315d753b 0.600000000000 1417476 of 15

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": 958133, "vin": [ { "gen": { "height": 958123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76b6a46ba5978940d2980d208de0a995aca078b0d288f6d808e66a6d315d753b" } } ], "extra": [ 1, 124, 70, 244, 210, 209, 207, 127, 81, 230, 202, 174, 22, 172, 93, 62, 6, 87, 139, 214, 42, 175, 95, 220, 166, 22, 212, 205, 165, 212, 168, 254, 43, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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