Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 257dcd506a4197dcb4cece335f1b7443e2dc4514a1d7d4be0961b3779b085b97

Tx prefix hash: 6bc073e095e8134eb3a2cbde6bf3d1fdf5af654b37c17348aff77379d2ed05e2
Tx public key: ed9eec82ef2acfbd73ed372ddb272bea31bfe2ffb76f2aaf6d440305253049ca
Timestamp: 1732330674 Timestamp [UCT]: 2024-11-23 02:57:54 Age [y:d:h:m:s]: 00:001:05:08:56
Block: 1159686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 869 RingCT/type: yes/0
Extra: 01ed9eec82ef2acfbd73ed372ddb272bea31bfe2ffb76f2aaf6d440305253049ca0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af039ad5d01430e3c78ef42796094cf4c991836d24eec33fa577c731d50d0b6b 0.600000000000 1645325 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": 1159696, "vin": [ { "gen": { "height": 1159686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af039ad5d01430e3c78ef42796094cf4c991836d24eec33fa577c731d50d0b6b" } } ], "extra": [ 1, 237, 158, 236, 130, 239, 42, 207, 189, 115, 237, 55, 45, 219, 39, 43, 234, 49, 191, 226, 255, 183, 111, 42, 175, 109, 68, 3, 5, 37, 48, 73, 202, 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