Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22118d427aefcdb2dfff4b2dc3b62e8c7d3bdc53d5b0ece0be80d502dcf79c04

Tx prefix hash: 48e35d3eab4febc6900584a5ae7a097606b467c14675448f03658db54c53d129
Tx public key: 605eeb21ad0fdde49eef97b0e7e07d16c50d3bdd235be28b37f55739f79f92a5
Timestamp: 1726743697 Timestamp [UCT]: 2024-09-19 11:01:37 Age [y:d:h:m:s]: 00:192:18:25:28
Block: 1113463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137585 RingCT/type: yes/0
Extra: 01605eeb21ad0fdde49eef97b0e7e07d16c50d3bdd235be28b37f55739f79f92a502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b90ecdf84c10f02026233255f5c82540aee49383b40a7c6bf743f1a8e8456a27 0.600000000000 1593142 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": 1113473, "vin": [ { "gen": { "height": 1113463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b90ecdf84c10f02026233255f5c82540aee49383b40a7c6bf743f1a8e8456a27" } } ], "extra": [ 1, 96, 94, 235, 33, 173, 15, 221, 228, 158, 239, 151, 176, 231, 224, 125, 22, 197, 13, 59, 221, 35, 91, 226, 139, 55, 245, 87, 57, 247, 159, 146, 165, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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