Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e93bc8bb1c8c4d38294f0aa0f631e77ee9c5003713935eaddd93bbd8331175a

Tx prefix hash: 390cdff0b38467fb03c4f88e42e4c6d2d4f81fd76791ad508fdb5577aa687bbd
Tx public key: ce01b5ca9c4ff272765d3027ee29b9a5436bb274a59f52f1221c80ee214fb393
Timestamp: 1660743939 Timestamp [UCT]: 2022-08-17 13:45:39 Age [y:d:h:m:s]: 02:245:18:59:23
Block: 567859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696885 RingCT/type: yes/0
Extra: 01ce01b5ca9c4ff272765d3027ee29b9a5436bb274a59f52f1221c80ee214fb39302110000000375e3f0e9000000000000000000

1 output(s) for total of 8.062087542000 dcy

stealth address amount amount idx
00: f86592f755a1452f0daef51d3a65bbed28e16769d984b481bb76f6a8fe3d6824 8.062087542000 1000966 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": 567869, "vin": [ { "gen": { "height": 567859 } } ], "vout": [ { "amount": 8062087542, "target": { "key": "f86592f755a1452f0daef51d3a65bbed28e16769d984b481bb76f6a8fe3d6824" } } ], "extra": [ 1, 206, 1, 181, 202, 156, 79, 242, 114, 118, 93, 48, 39, 238, 41, 185, 165, 67, 107, 178, 116, 165, 159, 82, 241, 34, 28, 128, 238, 33, 79, 179, 147, 2, 17, 0, 0, 0, 3, 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