Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc52385cb2a0be65ed6109781146fd2669ef18cd4c9b3be2ea826140c97dcc2

Tx prefix hash: 236302077d9b01d30089390b36f73f54baa83d39c375170d41d268f2f9fd69ed
Tx public key: 501ebc69a907b3126159fcf5048bc4e18d72d22c2e50b111b3b06465d48e5af4
Timestamp: 1743924279 Timestamp [UCT]: 2025-04-06 07:24:39 Age [y:d:h:m:s]: 00:058:02:54:36
Block: 1255397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41594 RingCT/type: yes/0
Extra: 01501ebc69a907b3126159fcf5048bc4e18d72d22c2e50b111b3b06465d48e5af4021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926cb2e68e92078f810e83e89efd7fd796f4afc04c274c83a39d65bab9cff696 0.600000000000 1742502 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": 1255407, "vin": [ { "gen": { "height": 1255397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926cb2e68e92078f810e83e89efd7fd796f4afc04c274c83a39d65bab9cff696" } } ], "extra": [ 1, 80, 30, 188, 105, 169, 7, 179, 18, 97, 89, 252, 245, 4, 139, 196, 225, 141, 114, 210, 44, 46, 80, 177, 17, 179, 176, 100, 101, 212, 142, 90, 244, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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