Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a7e40dd146f194786031a371f8912ee21cc96a1e091a2c5d2460c57e2864c0

Tx prefix hash: b525c0fc1c911f70739a28fc076994094cc82c2f0474e5170f586fa9e2f272a3
Tx public key: 9ef2a985c6a4bd5db138d577339d8e8ffa05bd19be0c2b5123d04fe1cdf8b0d9
Timestamp: 1737862992 Timestamp [UCT]: 2025-01-26 03:43:12 Age [y:d:h:m:s]: 00:325:08:46:24
Block: 1205445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230121 RingCT/type: yes/0
Extra: 019ef2a985c6a4bd5db138d577339d8e8ffa05bd19be0c2b5123d04fe1cdf8b0d90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941c9b7592bd3ef91e13ceae10d4b647a3c45c3d04cc9880deab90201a0b6613 0.600000000000 1692142 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": 1205455, "vin": [ { "gen": { "height": 1205445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941c9b7592bd3ef91e13ceae10d4b647a3c45c3d04cc9880deab90201a0b6613" } } ], "extra": [ 1, 158, 242, 169, 133, 198, 164, 189, 93, 177, 56, 213, 119, 51, 157, 142, 143, 250, 5, 189, 25, 190, 12, 43, 81, 35, 208, 79, 225, 205, 248, 176, 217, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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