Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed343f03e1b25e7054782ffd49a897c319ac5ee3c00a630f2a5447c2831bcda

Tx prefix hash: 4ac3647bd729715ded49a6ee02ed5d5d3f97535726bf7ed7f947dfce658741e4
Tx public key: 4671e1baf4866df7180254218090723044b2fad5d3894ec2c637d18a5aaa26c2
Timestamp: 1749725198 Timestamp [UCT]: 2025-06-12 10:46:38 Age [y:d:h:m:s]: 00:149:18:50:54
Block: 1303394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104766 RingCT/type: yes/0
Extra: 014671e1baf4866df7180254218090723044b2fad5d3894ec2c637d18a5aaa26c2021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4157b3bd9a45f7139a097a87c4cb4dcdc14ef0e39cffefe5d9d8243e74f3f740 0.600000000000 1790973 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": 1303404, "vin": [ { "gen": { "height": 1303394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4157b3bd9a45f7139a097a87c4cb4dcdc14ef0e39cffefe5d9d8243e74f3f740" } } ], "extra": [ 1, 70, 113, 225, 186, 244, 134, 109, 247, 24, 2, 84, 33, 128, 144, 114, 48, 68, 178, 250, 213, 211, 137, 78, 194, 198, 55, 209, 138, 90, 170, 38, 194, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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