Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b5a1c388f3b4d9ecd255913dc15992bc6b585048e718601aa30d5e00cb15be3

Tx prefix hash: 8fe5284cd736a1132516c25a79e72e6a8e62120db245ccf44ed77feec798c611
Tx public key: bc7e6cd909aeb2cd16ecdd254e6dcb8faabab5ddc38202fa2bfc748bfd103ba8
Timestamp: 1738251953 Timestamp [UCT]: 2025-01-30 15:45:53 Age [y:d:h:m:s]: 00:286:21:09:49
Block: 1208453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202791 RingCT/type: yes/0
Extra: 01bc7e6cd909aeb2cd16ecdd254e6dcb8faabab5ddc38202fa2bfc748bfd103ba8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da424f803db156034d51355c2e9e927726f6cf46c82c528ebdf452a416b7d7e3 0.600000000000 1695186 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": 1208463, "vin": [ { "gen": { "height": 1208453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da424f803db156034d51355c2e9e927726f6cf46c82c528ebdf452a416b7d7e3" } } ], "extra": [ 1, 188, 126, 108, 217, 9, 174, 178, 205, 22, 236, 221, 37, 78, 109, 203, 143, 170, 186, 181, 221, 195, 130, 2, 250, 43, 252, 116, 139, 253, 16, 59, 168, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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