Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 758d5bcf44994f6aec86976a359fadb2022f3b85db484f4909d3e074c8710236

Tx prefix hash: 59757b2602b9d00d927aa7a4300ed5aef9f9d114a4eb67ef1c6f6969e3f7dbac
Tx public key: 5bc4f3bcec100e5f8c31b08d0e101a5555b32ec73f5a1ded6989936e6388d6f5
Timestamp: 1744286861 Timestamp [UCT]: 2025-04-10 12:07:41 Age [y:d:h:m:s]: 00:214:19:29:24
Block: 1258405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151242 RingCT/type: yes/0
Extra: 015bc4f3bcec100e5f8c31b08d0e101a5555b32ec73f5a1ded6989936e6388d6f50211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8e7746625a70d11d5f3b9276d540af9500702b90972aec487749a9ec699fc49 0.600000000000 1745538 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": 1258415, "vin": [ { "gen": { "height": 1258405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8e7746625a70d11d5f3b9276d540af9500702b90972aec487749a9ec699fc49" } } ], "extra": [ 1, 91, 196, 243, 188, 236, 16, 14, 95, 140, 49, 176, 141, 14, 16, 26, 85, 85, 179, 46, 199, 63, 90, 29, 237, 105, 137, 147, 110, 99, 136, 214, 245, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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