Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b4faf8f504bcab7f0782c33c52452c6993371683bb4c1ad98f5799ba509b3e

Tx prefix hash: 40a4365343a0cef72c397d14a3b886e1ed5c0f112b967dd289edca160477cd0a
Tx public key: d75ee1d03a57aa29cc7a55930819a5b1ddb87c562e4ce75a539daa06b44a13d0
Timestamp: 1715262864 Timestamp [UCT]: 2024-05-09 13:54:24 Age [y:d:h:m:s]: 00:135:00:24:36
Block: 1018292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96706 RingCT/type: yes/0
Extra: 01d75ee1d03a57aa29cc7a55930819a5b1ddb87c562e4ce75a539daa06b44a13d002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3599a7beb8ec65a6290483eb4f703b25c4b746cab9b4483d3abcce0ef62a038 0.600000000000 1482081 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": 1018302, "vin": [ { "gen": { "height": 1018292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3599a7beb8ec65a6290483eb4f703b25c4b746cab9b4483d3abcce0ef62a038" } } ], "extra": [ 1, 215, 94, 225, 208, 58, 87, 170, 41, 204, 122, 85, 147, 8, 25, 165, 177, 221, 184, 124, 86, 46, 76, 231, 90, 83, 157, 170, 6, 180, 74, 19, 208, 2, 17, 0, 0, 0, 5, 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