Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c367eaca01a3bce7efdec4fec63922c33ba2d37db934b94c923af404d727069e

Tx prefix hash: dd1254b88bb89416834a81f0b1fbc6de0a36f38ad1b43b521e581ed2d14863e9
Tx public key: 67f44d5ec5ff87ff3ba3e356250966fa5f71a812d70f9f7150b65c06ec5ade4f
Timestamp: 1685099983 Timestamp [UCT]: 2023-05-26 11:19:43 Age [y:d:h:m:s]: 01:325:23:53:06
Block: 768468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494203 RingCT/type: yes/0
Extra: 0167f44d5ec5ff87ff3ba3e356250966fa5f71a812d70f9f7150b65c06ec5ade4f02110000000133af99f4000000000000000000

1 output(s) for total of 1.744804151000 dcy

stealth address amount amount idx
00: ad677cf6b3cf9973c77ccd47b1e51fd5bc0513be299e9ca5d223e0f2c0e44472 1.744804151000 1217669 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": 768478, "vin": [ { "gen": { "height": 768468 } } ], "vout": [ { "amount": 1744804151, "target": { "key": "ad677cf6b3cf9973c77ccd47b1e51fd5bc0513be299e9ca5d223e0f2c0e44472" } } ], "extra": [ 1, 103, 244, 77, 94, 197, 255, 135, 255, 59, 163, 227, 86, 37, 9, 102, 250, 95, 113, 168, 18, 215, 15, 159, 113, 80, 182, 92, 6, 236, 90, 222, 79, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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