Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4cf7ec5f963eb923992ad7038a29fd7a28fd8d7718ff4ad9de7a33265429ff

Tx prefix hash: 37efbaed6d949870d01aff0d5142abfcda4a0709822f6109727c0421aa843466
Tx public key: 3b95769a1d10cf3e6aaac31ae95ed1f0e5be3265dd6785e0819369f1230a1bbf
Timestamp: 1759255429 Timestamp [UCT]: 2025-09-30 18:03:49 Age [y:d:h:m:s]: 00:040:23:14:42
Block: 1379875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29346 RingCT/type: yes/0
Extra: 013b95769a1d10cf3e6aaac31ae95ed1f0e5be3265dd6785e0819369f1230a1bbf021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a936867e04b358cf356cbcfd1c24b2036e1347520fd7a794fcd013329f76a9 0.600000000000 1867986 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": 1379885, "vin": [ { "gen": { "height": 1379875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a936867e04b358cf356cbcfd1c24b2036e1347520fd7a794fcd013329f76a9" } } ], "extra": [ 1, 59, 149, 118, 154, 29, 16, 207, 62, 106, 170, 195, 26, 233, 94, 209, 240, 229, 190, 50, 101, 221, 103, 133, 224, 129, 147, 105, 241, 35, 10, 27, 191, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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