Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b141296e6c5248d3f3e09e79c4003689f059dc01a0a737f5eb6e54614fe414f

Tx prefix hash: ed8fe1a77f9bcd1597b760aa11e21f8daf7b7a5edec34ae4c27cf5c65c811027
Tx public key: 518146adfa5ecc04e7e8b50d77e335fbbce177a0cddd17fd1d1e9eee17a8cba0
Timestamp: 1633446758 Timestamp [UCT]: 2021-10-05 15:12:38 Age [y:d:h:m:s]: 03:085:08:11:59
Block: 347220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 838115 RingCT/type: yes/0
Extra: 01518146adfa5ecc04e7e8b50d77e335fbbce177a0cddd17fd1d1e9eee17a8cba0021100000001a272b9cb000000000000000000

1 output(s) for total of 43.403418234000 dcy

stealth address amount amount idx
00: ff79c76824089d98162e97fc776cb2072ba01a1854bfa25980e10ac35fbdfd80 43.403418234000 711564 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": 347230, "vin": [ { "gen": { "height": 347220 } } ], "vout": [ { "amount": 43403418234, "target": { "key": "ff79c76824089d98162e97fc776cb2072ba01a1854bfa25980e10ac35fbdfd80" } } ], "extra": [ 1, 81, 129, 70, 173, 250, 94, 204, 4, 231, 232, 181, 13, 119, 227, 53, 251, 188, 225, 119, 160, 205, 221, 23, 253, 29, 30, 158, 238, 23, 168, 203, 160, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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