Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9736b35a41e098309e8dc2fbae59516464bd9b6aff7e9df0501d37d301a102fa

Tx prefix hash: 35da189fa1ae446c3796052bde345b712b4fbaa378f216d96bb59c11bb844892
Tx public key: 8b8e3d7b59bb0fa3b18bfcc37225b1277a2595f94dcae2ca9862adf0dd522d3e
Timestamp: 1709400629 Timestamp [UCT]: 2024-03-02 17:30:29 Age [y:d:h:m:s]: 00:267:11:11:51
Block: 969689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191472 RingCT/type: yes/0
Extra: 018b8e3d7b59bb0fa3b18bfcc37225b1277a2595f94dcae2ca9862adf0dd522d3e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df9263edc5a7e856b2ae85fd74f43ce7cdca8a9b6999acaf33822215d91bcee8 0.600000000000 1429526 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": 969699, "vin": [ { "gen": { "height": 969689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df9263edc5a7e856b2ae85fd74f43ce7cdca8a9b6999acaf33822215d91bcee8" } } ], "extra": [ 1, 139, 142, 61, 123, 89, 187, 15, 163, 177, 139, 252, 195, 114, 37, 177, 39, 122, 37, 149, 249, 77, 202, 226, 202, 152, 98, 173, 240, 221, 82, 45, 62, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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