Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f526c51fe90c14a451c8b12c771b7cd02cb7daeffd41fe807b1482062c9e5e7c

Tx prefix hash: 8e9ef62772d01293e3b036b6dc312363b34bc15c94b32cfc5c7a70d622425917
Tx public key: b91e0376bd0adcf272b970a02c1a9e7684c14d4fe5b6a2ff5e5553ed87222bbe
Timestamp: 1694741811 Timestamp [UCT]: 2023-09-15 01:36:51 Age [y:d:h:m:s]: 01:131:02:16:40
Block: 848334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354979 RingCT/type: yes/0
Extra: 01b91e0376bd0adcf272b970a02c1a9e7684c14d4fe5b6a2ff5e5553ed87222bbe021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.948674784000 dcy

stealth address amount amount idx
00: b200f6d636f4860936d9e0c25e9f903ee883c0d5bc6a1d5483e4a852e6f1a645 0.948674784000 1301930 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": 848344, "vin": [ { "gen": { "height": 848334 } } ], "vout": [ { "amount": 948674784, "target": { "key": "b200f6d636f4860936d9e0c25e9f903ee883c0d5bc6a1d5483e4a852e6f1a645" } } ], "extra": [ 1, 185, 30, 3, 118, 189, 10, 220, 242, 114, 185, 112, 160, 44, 26, 158, 118, 132, 193, 77, 79, 229, 182, 162, 255, 94, 85, 83, 237, 135, 34, 43, 190, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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