Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a592739bfa4e33e0c0b5f402d037df24fee0d0e2a262ee462c63c59d5c387a2a

Tx prefix hash: 27fbd89777a1ab4b53477a6f22487a4d7d463412bacbae2477b406db66d7c1a7
Tx public key: fd7ac816f443c3f8b57b2c944065d6076f5332f33355e48af08e03a9f77594a5
Timestamp: 1699603334 Timestamp [UCT]: 2023-11-10 08:02:14 Age [y:d:h:m:s]: 01:224:01:35:45
Block: 888467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421202 RingCT/type: yes/0
Extra: 01fd7ac816f443c3f8b57b2c944065d6076f5332f33355e48af08e03a9f77594a502110000000333af99f4000000000000000000

1 output(s) for total of 0.698457538000 dcy

stealth address amount amount idx
00: 2f3cdb540c30e9c2d6108a34cbcff1e55d3b9e49b8ad0b0ebb681ce48156a296 0.698457538000 1344410 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": 888477, "vin": [ { "gen": { "height": 888467 } } ], "vout": [ { "amount": 698457538, "target": { "key": "2f3cdb540c30e9c2d6108a34cbcff1e55d3b9e49b8ad0b0ebb681ce48156a296" } } ], "extra": [ 1, 253, 122, 200, 22, 244, 67, 195, 248, 181, 123, 44, 148, 64, 101, 214, 7, 111, 83, 50, 243, 51, 85, 228, 138, 240, 142, 3, 169, 247, 117, 148, 165, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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