Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f90ae38b5f5246254e2441c35a1e6a727a1573ed1dab05acab5a3b5e249289d

Tx prefix hash: 98db0e8bb32901e5b1c0e5d556b53de57146499681623a52d9181b31275ae252
Tx public key: 35ab87a2a93549ce27d725f8e78531dd299de231e3687f2004d9216f572cf46c
Timestamp: 1673113160 Timestamp [UCT]: 2023-01-07 17:39:20 Age [y:d:h:m:s]: 02:275:07:22:21
Block: 669697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716134 RingCT/type: yes/0
Extra: 0135ab87a2a93549ce27d725f8e78531dd299de231e3687f2004d9216f572cf46c02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.706942011000 dcy

stealth address amount amount idx
00: 1d5a32be6ec27659df17faff3c0748df98f6ec11a3fa18dffc067e8a43abd269 3.706942011000 1111054 of 0

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": 669707, "vin": [ { "gen": { "height": 669697 } } ], "vout": [ { "amount": 3706942011, "target": { "key": "1d5a32be6ec27659df17faff3c0748df98f6ec11a3fa18dffc067e8a43abd269" } } ], "extra": [ 1, 53, 171, 135, 162, 169, 53, 73, 206, 39, 215, 37, 248, 231, 133, 49, 221, 41, 157, 226, 49, 227, 104, 127, 32, 4, 217, 33, 111, 87, 44, 244, 108, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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