Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93df45625ed126f0b62d6fd5e9b982d56212082f824f0d2e3ef1f03cdb8fa943

Tx prefix hash: 40b95ea66ce5211a93ceafe3cb5db232f00b09a66673931f558f366149dce3e1
Tx public key: a79141681dfc343ad6a5914797009b07d4dccc624c8b036592c99bbb68e8ffb3
Timestamp: 1762918734 Timestamp [UCT]: 2025-11-12 03:38:54 Age [y:d:h:m:s]: 00:052:20:02:14
Block: 1410251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37834 RingCT/type: yes/0
Extra: 01a79141681dfc343ad6a5914797009b07d4dccc624c8b036592c99bbb68e8ffb3021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74b55bbeed459f4b197c7819a91928a2b4fddf6367341444b68b83df7bdec0a1 0.600000000000 1898702 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": 1410261, "vin": [ { "gen": { "height": 1410251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74b55bbeed459f4b197c7819a91928a2b4fddf6367341444b68b83df7bdec0a1" } } ], "extra": [ 1, 167, 145, 65, 104, 29, 252, 52, 58, 214, 165, 145, 71, 151, 0, 155, 7, 212, 220, 204, 98, 76, 139, 3, 101, 146, 201, 155, 187, 104, 232, 255, 179, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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